Missing dependency GLMHighlighterTextStylerDecorator in Pharo 9

Question

Missing dependency GLMHighlighterTextStylerDecorator in Pharo 9

Closed this issue 3 years ago · 7 comments

StewMacLean commented 3 years ago

When loading I found that GLMHighlighterTextStylerDecorator has been removed in Pharo 9

The workaround was to ignore the error and return nil to continue loading.

This worked for me as I just needed the core serialisation to convert objects from VisualWorks.

Thanks for this functionality - saved me a heap of "reentry"!

Answer 1 · 2022-04-01T05:49:09.000Z

Thank you for your report.
The warning is probably related to the prerequisite XMLParser. I'll fix it soon.

Answer 2 · 2022-04-01T12:29:20.000Z

I've made a pull request. It will be merged after testing.
#12

Answer 3 · 2022-04-01T13:33:10.000Z

Now tests are all green! Please try the latest master (v0.5.3)

.

Answer 4 · 2022-04-04T13:40:26.000Z

Now close the issue. Please let me know if there any problems.

Answer 5 · 2022-04-04T21:38:29.000Z

Thanks Masashi for developing this package and this fix. It saved me a lot of time exporting some objects from VisualWorks to Pharo! Thanks! I did notice that you have done some work with the Objectivity graph database. I don't have a requirement for a database at the moment, but when I was looking at developing a business application I did enquire whether they still had Smalltalk bindings. Unfortunately, they no longer supported it. Do you know if they have changed and will support Smalltalk/Pharo? Cheers, Stewart

…

On Fri, Apr 1, 2022 at 6:49 PM Masashi Umezawa ***@***.***> wrote: Thank you for your report. The warning is probably related to the prerequisite XMLParser. I'll fix it soon. — Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXGQYQ5K52GOJH765GR7AILVC2E57ANCNFSM5SGSRWTA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Answer 6 · 2022-04-05T09:20:26.000Z

Unfortunately, I'm not sure Objectivity/Smalltalk is still supported by Objectivity/DB.
It had nice declarative relationships support, and I liked it a lot. However, it did not gain popularity.

If you are looking for a graph database, Neo4j will be a good candidate.

I've developed some connectors for Pharo.
https://github.com/mumez/Neo4reSt (REST connector)
https://github.com/mumez/SCypherGraph (FFI connector)

Neo4reSt would be easily ported to VW, since it only relies on http client.

If you prefer more orthgonal persistence, I recommend GemStone/S.
Now they offer a starter plan, and it is enough for small applications.
https://gemtalksystems.com/licensing/

Answer 7 · 2022-04-05T21:20:40.000Z

Hey thanks for this - I'm currently using Fuel as my object graphs are small and I load them in entirety. However, this looks very useful for a persistence back end for bigger data sets. ORM to be avoided at all costs! Cheers, Stewart

…

On Tue, Apr 5, 2022 at 9:20 PM Masashi Umezawa ***@***.***> wrote: Unfortunately, I'm not sure Objectivity/Smalltalk is still supported by Objectivity/DB. It had nice declarative relationships support, and I liked it a lot. However, it did not gain popularity. If you are looking for a graph database, Neo4j will be a good candidate. I've developed some connectors for Pharo. https://github.com/mumez/Neo4reSt (REST connector) https://github.com/mumez/SCypherGraph (FFI connector) Neo4reSt would be easily ported to VW, since it only relies on http client. If you prefer more orthgonal persistence, I recommend GemStone/S. Now they offer a starter plan, and it is enough for small applications. https://gemtalksystems.com/licensing/ — Reply to this email directly, view it on GitHub <#9 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXGQYQ35XUIQLJH37DQV3ETVDQAWLANCNFSM5SGSRWTA> . You are receiving this because you authored the thread.Message ID: ***@***.***>