Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

Steffen Märcker
Hi,

I tried the tool yesterday and found some hickups. After opening issues on  
GitHub, I wonder how I can easily contribute a PR there. I imagine there  
is a straight-forward way with Iceberg now, isn't it? I a sorry if I miss  
the obvious but I am still not familiar with Pharos comprehensive tool set.

Best, Steffen


Am .10.2018, 18:06 Uhr, schrieb milton mamani <[hidden email]>:

> Hi you can use
>
> https://github.com/ObjectProfile/Pharo2VW
>
> Cheers, Milton
>
> El sáb., 13 oct. 2018 a las 12:38, Steffen Märcker (<[hidden email]>)
> escribió:
>
>> Hi,
>>
>> I gave PetitParser 2 a try and I am pretty impressed by the results,
>> please see the updated table below. =) Again, that's pure parsing and
>> Array-based AST-building. Moving to PP2 was indeed as easy as sending
>> #asPParser and working around character ranges ($a - $z). Is there a
>> preferred way to do the latter?
>>
>> Jan mentioned that there might be an automated tool to port stuff to
>> VisualWorks. Do you have a name? And again the old question: what is the
>> preferred workflow to exchange code between the two dialects? Till now I
>> stick to FileOut30.
>>
>> input  Prism        Storm  Xtreams.PEG  PP     PP2
>> size   parse check  check  parse cache  parse  parse optim
>> 230kB   0.1s   10s     6s     9s    3s     2s     4s  0.2s
>> 544kB   0.2s   90s    20s    20s    7s     5s     9s  0.5s
>> 1.1MB   0.4s  392s    46s    34s   13s     8s    15s  1.0s
>> 1.4MB   0.8s 1091s    85s    47s   20s    12s    20s  1.3s
>> 2.2MB                        63s   30s    16s    27s  1.9s
>> 2.9MB                        81s   44s    20s    34s  2.5s
>> 3.8MB                       107s   61s    25s    45s  3.1s
>> 4.4MB                       123s   76s    30s    56s  3.7s
>>
>> Best, Steffen
>>
>>
>> Am .10.2018, 05:22 Uhr, schrieb Tudor Girba <[hidden email]>:
>>
>> > Hi,
>> >
>> > Interesting experiment. Thanks for sharing!
>> >
>> > I assume that you tried the original PetitParser. PetitParser2 offers
>> > the possibility to optimize the parser (kind of a compilation), and
>> this
>> > provides a significant speedup:
>> > https://github.com/kursjan/petitparser2
>> >
>> > Would you be interested in trying this out?
>> >
>> > Cheers,
>> > Doru
>> >
>> >
>> >
>> >> On Oct 4, 2018, at 10:46 PM, Steffen Märcker <[hidden email]> wrote:
>> >>
>> >> I gave Xtreams-Parsing and PetitParser a shot and like to share my
>> >> findings.[*]
>> >>
>> >> The task was to parse the modelling language of the probabilistic
>> model
>> >> checker PRISM. I've written a grammer of about 130 definitions in the
>> >> Xtreams DSL, which is close to Bryan Fords syntax. To avoid doing it
>> >> all again with PetitParser, I wrote a PetitParserGenerator that takes
>> >> the DSL and builds a PetitParser.
>> >>
>> >> The numbers below are just parsing times, no further actions  
>> involved.
>> >> For reference I show the times from PRISM (which uses JavaCC), too --
>> >> although they involve additional verification and normalization steps
>> >> on the AST.
>> >>
>> >> input  Prism    XP   PP
>> >> 230kB    14s    9s   2s
>> >> 544kB        121s   20s   5s
>> >> 1.1MB        421s   34s   8s
>> >> 1.4MB  1091s   47s  12s
>> >> 2.2MB          63s  16s
>> >> 2.9MB          81s  20s
>> >> 3.8MB         107s  25s
>> >> 4.4MB         123s  30s
>> >>
>> >> Please note that these times are not representative at all. It's just
>> a
>> >> single example and I put zero effort in optimization. However, I am
>> >> quite satisfied with the results.
>> >>
>> >> [*] I was already familiar with the DSL of Xtreams-Parsing, which I
>> >> like very much. I did not consider SmaCC, as I find PEGs easier to  
>> use.
>> >>
>> >> Best, Steffen
>> >>
>> >>
>> >>
>> >> Am .10.2018, 20:14 Uhr, schrieb Steffen Märcker <[hidden email]>:
>> >>
>> >>> Dear all,
>> >>>
>> >>> I have two questions regarding parsing frameworks.
>> >>>
>> >>> 1) Do you have any insights on the performance of SmaCC VS Xtreams
>> >>> Parsing VS PetitParser?
>> >>> 2) Has anybody started to port PetitParser 2 from Pharo to VW? Is it
>> >>> worth the effort?
>> >>>
>> >>> Sorry for cross-posting, I thought this might interest both
>> >>> communities.
>> >>>
>> >>> Cheers, Steffen
>> >
>> > --
>> > www.feenk.com
>> >
>> > "No matter how many recipes we know, we still value a chef."
>> >
>> >
>> >
>> >
>> >
>> >
>> >

Reply | Threaded
Open this post in threaded view
|

Re: Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

Steffen Märcker
Nevermind, I figured it out easily. Must been blind before.

Many thanks to the Iceberg team, the tool works like a charm in 6.1!


Am .10.2018, 10:58 Uhr, schrieb Steffen Märcker <[hidden email]>:

> Hi,
>
> I tried the tool yesterday and found some hickups. After opening issues  
> on GitHub, I wonder how I can easily contribute a PR there. I imagine  
> there is a straight-forward way with Iceberg now, isn't it? I a sorry if  
> I miss the obvious but I am still not familiar with Pharos comprehensive  
> tool set.
>
> Best, Steffen
>
>
> Am .10.2018, 18:06 Uhr, schrieb milton mamani <[hidden email]>:
>
>> Hi you can use
>>
>> https://github.com/ObjectProfile/Pharo2VW
>>
>> Cheers, Milton
>>
>> El sáb., 13 oct. 2018 a las 12:38, Steffen Märcker (<[hidden email]>)
>> escribió:
>>
>>> Hi,
>>>
>>> I gave PetitParser 2 a try and I am pretty impressed by the results,
>>> please see the updated table below. =) Again, that's pure parsing and
>>> Array-based AST-building. Moving to PP2 was indeed as easy as sending
>>> #asPParser and working around character ranges ($a - $z). Is there a
>>> preferred way to do the latter?
>>>
>>> Jan mentioned that there might be an automated tool to port stuff to
>>> VisualWorks. Do you have a name? And again the old question: what is  
>>> the
>>> preferred workflow to exchange code between the two dialects? Till now  
>>> I
>>> stick to FileOut30.
>>>
>>> input  Prism        Storm  Xtreams.PEG  PP     PP2
>>> size   parse check  check  parse cache  parse  parse optim
>>> 230kB   0.1s   10s     6s     9s    3s     2s     4s  0.2s
>>> 544kB   0.2s   90s    20s    20s    7s     5s     9s  0.5s
>>> 1.1MB   0.4s  392s    46s    34s   13s     8s    15s  1.0s
>>> 1.4MB   0.8s 1091s    85s    47s   20s    12s    20s  1.3s
>>> 2.2MB                        63s   30s    16s    27s  1.9s
>>> 2.9MB                        81s   44s    20s    34s  2.5s
>>> 3.8MB                       107s   61s    25s    45s  3.1s
>>> 4.4MB                       123s   76s    30s    56s  3.7s
>>>
>>> Best, Steffen
>>>
>>>
>>> Am .10.2018, 05:22 Uhr, schrieb Tudor Girba <[hidden email]>:
>>>
>>> > Hi,
>>> >
>>> > Interesting experiment. Thanks for sharing!
>>> >
>>> > I assume that you tried the original PetitParser. PetitParser2 offers
>>> > the possibility to optimize the parser (kind of a compilation), and
>>> this
>>> > provides a significant speedup:
>>> > https://github.com/kursjan/petitparser2
>>> >
>>> > Would you be interested in trying this out?
>>> >
>>> > Cheers,
>>> > Doru
>>> >
>>> >
>>> >
>>> >> On Oct 4, 2018, at 10:46 PM, Steffen Märcker <[hidden email]> wrote:
>>> >>
>>> >> I gave Xtreams-Parsing and PetitParser a shot and like to share my
>>> >> findings.[*]
>>> >>
>>> >> The task was to parse the modelling language of the probabilistic
>>> model
>>> >> checker PRISM. I've written a grammer of about 130 definitions in  
>>> the
>>> >> Xtreams DSL, which is close to Bryan Fords syntax. To avoid doing it
>>> >> all again with PetitParser, I wrote a PetitParserGenerator that  
>>> takes
>>> >> the DSL and builds a PetitParser.
>>> >>
>>> >> The numbers below are just parsing times, no further actions  
>>> involved.
>>> >> For reference I show the times from PRISM (which uses JavaCC), too  
>>> --
>>> >> although they involve additional verification and normalization  
>>> steps
>>> >> on the AST.
>>> >>
>>> >> input  Prism    XP   PP
>>> >> 230kB    14s    9s   2s
>>> >> 544kB        121s   20s   5s
>>> >> 1.1MB        421s   34s   8s
>>> >> 1.4MB  1091s   47s  12s
>>> >> 2.2MB          63s  16s
>>> >> 2.9MB          81s  20s
>>> >> 3.8MB         107s  25s
>>> >> 4.4MB         123s  30s
>>> >>
>>> >> Please note that these times are not representative at all. It's  
>>> just
>>> a
>>> >> single example and I put zero effort in optimization. However, I am
>>> >> quite satisfied with the results.
>>> >>
>>> >> [*] I was already familiar with the DSL of Xtreams-Parsing, which I
>>> >> like very much. I did not consider SmaCC, as I find PEGs easier to  
>>> use.
>>> >>
>>> >> Best, Steffen
>>> >>
>>> >>
>>> >>
>>> >> Am .10.2018, 20:14 Uhr, schrieb Steffen Märcker <[hidden email]>:
>>> >>
>>> >>> Dear all,
>>> >>>
>>> >>> I have two questions regarding parsing frameworks.
>>> >>>
>>> >>> 1) Do you have any insights on the performance of SmaCC VS Xtreams
>>> >>> Parsing VS PetitParser?
>>> >>> 2) Has anybody started to port PetitParser 2 from Pharo to VW? Is  
>>> it
>>> >>> worth the effort?
>>> >>>
>>> >>> Sorry for cross-posting, I thought this might interest both
>>> >>> communities.
>>> >>>
>>> >>> Cheers, Steffen
>>> >
>>> > --
>>> > www.feenk.com
>>> >
>>> > "No matter how many recipes we know, we still value a chef."
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >

Reply | Threaded
Open this post in threaded view
|

Re: Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

Pharo Smalltalk Users mailing list
Thanks Steffen for your contribution to Pharo2VW.
We reviewed and accepted your PullRequests.

Alexandre

> On Oct 19, 2018, at 6:29 AM, Steffen Märcker <[hidden email]> wrote:
>
> Nevermind, I figured it out easily. Must been blind before.
>
> Many thanks to the Iceberg team, the tool works like a charm in 6.1!
>
>
> Am .10.2018, 10:58 Uhr, schrieb Steffen Märcker <[hidden email]>:
>
>> Hi,
>>
>> I tried the tool yesterday and found some hickups. After opening issues on GitHub, I wonder how I can easily contribute a PR there. I imagine there is a straight-forward way with Iceberg now, isn't it? I a sorry if I miss the obvious but I am still not familiar with Pharos comprehensive tool set.
>>
>> Best, Steffen
>>
>>
>> Am .10.2018, 18:06 Uhr, schrieb milton mamani <[hidden email]>:
>>
>>> Hi you can use
>>>
>>> https://github.com/ObjectProfile/Pharo2VW
>>>
>>> Cheers, Milton
>>>
>>> El sáb., 13 oct. 2018 a las 12:38, Steffen Märcker (<[hidden email]>)
>>> escribió:
>>>
>>>> Hi,
>>>>
>>>> I gave PetitParser 2 a try and I am pretty impressed by the results,
>>>> please see the updated table below. =) Again, that's pure parsing and
>>>> Array-based AST-building. Moving to PP2 was indeed as easy as sending
>>>> #asPParser and working around character ranges ($a - $z). Is there a
>>>> preferred way to do the latter?
>>>>
>>>> Jan mentioned that there might be an automated tool to port stuff to
>>>> VisualWorks. Do you have a name? And again the old question: what is the
>>>> preferred workflow to exchange code between the two dialects? Till now I
>>>> stick to FileOut30.
>>>>
>>>> input  Prism        Storm  Xtreams.PEG  PP     PP2
>>>> size   parse check  check  parse cache  parse  parse optim
>>>> 230kB   0.1s   10s     6s     9s    3s     2s     4s  0.2s
>>>> 544kB   0.2s   90s    20s    20s    7s     5s     9s  0.5s
>>>> 1.1MB   0.4s  392s    46s    34s   13s     8s    15s  1.0s
>>>> 1.4MB   0.8s 1091s    85s    47s   20s    12s    20s  1.3s
>>>> 2.2MB                        63s   30s    16s    27s  1.9s
>>>> 2.9MB                        81s   44s    20s    34s  2.5s
>>>> 3.8MB                       107s   61s    25s    45s  3.1s
>>>> 4.4MB                       123s   76s    30s    56s  3.7s
>>>>
>>>> Best, Steffen
>>>>
>>>>
>>>> Am .10.2018, 05:22 Uhr, schrieb Tudor Girba <[hidden email]>:
>>>>
>>>> > Hi,
>>>> >
>>>> > Interesting experiment. Thanks for sharing!
>>>> >
>>>> > I assume that you tried the original PetitParser. PetitParser2 offers
>>>> > the possibility to optimize the parser (kind of a compilation), and
>>>> this
>>>> > provides a significant speedup:
>>>> > https://github.com/kursjan/petitparser2
>>>> >
>>>> > Would you be interested in trying this out?
>>>> >
>>>> > Cheers,
>>>> > Doru
>>>> >
>>>> >
>>>> >
>>>> >> On Oct 4, 2018, at 10:46 PM, Steffen Märcker <[hidden email]> wrote:
>>>> >>
>>>> >> I gave Xtreams-Parsing and PetitParser a shot and like to share my
>>>> >> findings.[*]
>>>> >>
>>>> >> The task was to parse the modelling language of the probabilistic
>>>> model
>>>> >> checker PRISM. I've written a grammer of about 130 definitions in the
>>>> >> Xtreams DSL, which is close to Bryan Fords syntax. To avoid doing it
>>>> >> all again with PetitParser, I wrote a PetitParserGenerator that takes
>>>> >> the DSL and builds a PetitParser.
>>>> >>
>>>> >> The numbers below are just parsing times, no further actions involved.
>>>> >> For reference I show the times from PRISM (which uses JavaCC), too --
>>>> >> although they involve additional verification and normalization steps
>>>> >> on the AST.
>>>> >>
>>>> >> input  Prism    XP   PP
>>>> >> 230kB    14s    9s   2s
>>>> >> 544kB        121s   20s   5s
>>>> >> 1.1MB        421s   34s   8s
>>>> >> 1.4MB  1091s   47s  12s
>>>> >> 2.2MB          63s  16s
>>>> >> 2.9MB          81s  20s
>>>> >> 3.8MB         107s  25s
>>>> >> 4.4MB         123s  30s
>>>> >>
>>>> >> Please note that these times are not representative at all. It's just
>>>> a
>>>> >> single example and I put zero effort in optimization. However, I am
>>>> >> quite satisfied with the results.
>>>> >>
>>>> >> [*] I was already familiar with the DSL of Xtreams-Parsing, which I
>>>> >> like very much. I did not consider SmaCC, as I find PEGs easier to use.
>>>> >>
>>>> >> Best, Steffen
>>>> >>
>>>> >>
>>>> >>
>>>> >> Am .10.2018, 20:14 Uhr, schrieb Steffen Märcker <[hidden email]>:
>>>> >>
>>>> >>> Dear all,
>>>> >>>
>>>> >>> I have two questions regarding parsing frameworks.
>>>> >>>
>>>> >>> 1) Do you have any insights on the performance of SmaCC VS Xtreams
>>>> >>> Parsing VS PetitParser?
>>>> >>> 2) Has anybody started to port PetitParser 2 from Pharo to VW? Is it
>>>> >>> worth the effort?
>>>> >>>
>>>> >>> Sorry for cross-posting, I thought this might interest both
>>>> >>> communities.
>>>> >>>
>>>> >>> Cheers, Steffen
>>>> >
>>>> > --
>>>> > www.feenk.com
>>>> >
>>>> > "No matter how many recipes we know, we still value a chef."
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>


Reply | Threaded
Open this post in threaded view
|

Re: Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

Steffen Märcker
You're welcome. =) I really like the tool as it makes cross-platform-life  
a lot easier. I really wish there was a similar tool for the reverse  
direction, too!

Cheers! Steffen

Am .10.2018, 22:38 Uhr, schrieb Alexandre Bergel via Pharo-users  
<[hidden email]>:

> Thanks Steffen for your contribution to Pharo2VW.
> We reviewed and accepted your PullRequests.
>
> Alexandre
>
>> On Oct 19, 2018, at 6:29 AM, Steffen Märcker <[hidden email]> wrote:
>>
>> Nevermind, I figured it out easily. Must been blind before.
>>
>> Many thanks to the Iceberg team, the tool works like a charm in 6.1!
>>
>>
>> Am .10.2018, 10:58 Uhr, schrieb Steffen Märcker <[hidden email]>:
>>
<---Schnitt--->
>>
>
>



Reply | Threaded
Open this post in threaded view
|

Re: Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

Pharo Smalltalk Users mailing list
>  I really like the tool as it makes cross-platform-life a lot easier.

Thanks :-)

> I really wish there was a similar tool for the reverse direction, too!

That is interesting. Anyone else interested in such a tool?

Cheers,
Alexandre


>
> Cheers! Steffen
>
> Am .10.2018, 22:38 Uhr, schrieb Alexandre Bergel via Pharo-users <[hidden email]>:
>
>> Thanks Steffen for your contribution to Pharo2VW.
>> We reviewed and accepted your PullRequests.
>>
>> Alexandre
>>
>>> On Oct 19, 2018, at 6:29 AM, Steffen Märcker <[hidden email]> wrote:
>>>
>>> Nevermind, I figured it out easily. Must been blind before.
>>>
>>> Many thanks to the Iceberg team, the tool works like a charm in 6.1!
>>>
>>>
>>> Am .10.2018, 10:58 Uhr, schrieb Steffen Märcker <[hidden email]>:
>>>
> <---Schnitt--->
>>>
>>
>>
>
>
>


Reply | Threaded
Open this post in threaded view
|

VW2Pharo ? (Was: Pharo2VW (Was:[vwnc] Parsing in Smalltalk))

cedreek

Objet: Rép : [Pharo-users] Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

I really like the tool as it makes cross-platform-life a lot easier.

Thanks :-)

I really wish there was a similar tool for the reverse direction, too!

That is interesting. Anyone else interested in such a tool?


A tool to port from VW to Pharo ?

Me interested, at least to port Christian work on RDF :)

Cheers,

Cédrick





Cheers,
Alexandre



Cheers! Steffen

Am .10.2018, 22:38 Uhr, schrieb Alexandre Bergel via Pharo-users <[hidden email]>:

Thanks Steffen for your contribution to Pharo2VW.
We reviewed and accepted your PullRequests.

Alexandre

On Oct 19, 2018, at 6:29 AM, Steffen Märcker <[hidden email]> wrote:

Nevermind, I figured it out easily. Must been blind before.

Many thanks to the Iceberg team, the tool works like a charm in 6.1!


Am .10.2018, 10:58 Uhr, schrieb Steffen Märcker <[hidden email]>:

<---Schnitt--->











Reply | Threaded
Open this post in threaded view
|

Re: VW2Pharo ? (Was: Pharo2VW (Was:[vwnc] Parsing in Smalltalk))

Christian Haider

Hi,

 

I did a tool for porting PDFtalk from VW to Gemstone (bundle {Gemstone Fileout Project}) .

When I have time, I plan to extend it for Pharo in order to port RDF (and Values).

I am thinking of making Pharo my RDF engine… we’ll see…

 

Happy hacking,

                Christian

 

Von: Cédrick Béler <[hidden email]>
Gesendet: Mittwoch, 14. November 2018 21:23
An: Any question about pharo is welcome <[hidden email]>
Cc: Christian Haider <[hidden email]>; Christian Haider <[hidden email]>
Betreff: VW2Pharo ? (Was: Pharo2VW (Was:[vwnc] Parsing in Smalltalk))

 

 

Objet: Rép : [Pharo-users] Pharo2VW (Was:[vwnc] Parsing in Smalltalk)

 

I really like the tool as it makes cross-platform-life a lot easier.


Thanks :-)


I really wish there was a similar tool for the reverse direction, too!


That is interesting. Anyone else interested in such a tool?

 

 

A tool to port from VW to Pharo ?

 

Me interested, at least to port Christian work on RDF :)

 

Cheers,

 

Cédrick

 

 

 




Cheers,
Alexandre




Cheers! Steffen

Am .10.2018, 22:38 Uhr, schrieb Alexandre Bergel via Pharo-users <[hidden email]>:


Thanks Steffen for your contribution to Pharo2VW.
We reviewed and accepted your PullRequests.

Alexandre


On Oct 19, 2018, at 6:29 AM, Steffen Märcker <[hidden email]> wrote:

Nevermind, I figured it out easily. Must been blind before.

Many thanks to the Iceberg team, the tool works like a charm in 6.1!


Am .10.2018, 10:58 Uhr, schrieb Steffen Märcker <[hidden email]>:

<---Schnitt--->

 

 






 

Reply | Threaded
Open this post in threaded view
|

Re: VW2Pharo ? (Was: Pharo2VW (Was:[vwnc] Parsing in Smalltalk))

Steffen Märcker
Please let me know if I can help with that porting tool! Btw, is it RDF  
like Resource Description Framework?

Dreamer mode: It would be awesome to teach VW tonel and Git for export and  
versioning!

Best, Steffen

Am .11.2018, 11:37 Uhr, schrieb Christian Haider  
<[hidden email]>:

> Hi,
>
>
> I did a tool for porting PDFtalk from VW to Gemstone (bundle {Gemstone  
> Fileout Project}) .
>
> When I have time, I plan to extend it for Pharo in order to port RDF  
> (and Values).
>
> I am thinking of making Pharo my RDF engine… we’ll see…
>
>
> Happy hacking,
>
>                 Christian
>
>
> Von: Cédrick Béler <[hidden email]>
> Gesendet: Mittwoch, 14. November 2018 21:23
> An: Any question about pharo is welcome <[hidden email]>
> Cc: Christian Haider <[hidden email]>;  
> Christian Haider <[hidden email]>
> Betreff: VW2Pharo ? (Was: Pharo2VW (Was:[vwnc] Parsing in Smalltalk))
>
>
>
> Objet: Rép : [Pharo-users] Pharo2VW (Was:[vwnc] Parsing in Smalltalk)
>
>
> I really like the tool as it makes cross-platform-life a lot easier.
>
>
> Thanks :-)
>
>
>
>
> I really wish there was a similar tool for the reverse direction, too!
>
>
> That is interesting. Anyone else interested in such a tool?
>
>
>
> A tool to port from VW to Pharo ?
>
>
> Me interested, at least to port Christian work on RDF :)
>
>
> Cheers,
>
>
> Cédrick
>
>
>
>
>
>
>
>
>
> Cheers,
> Alexandre
>
>
>
>
>
>
> Cheers! Steffen
>
> Am .10.2018, 22:38 Uhr, schrieb Alexandre Bergel via Pharo-users  
> <[hidden email] <mailto:[hidden email]> >:
>
>
>
>
> Thanks Steffen for your contribution to Pharo2VW.
> We reviewed and accepted your PullRequests.
>
> Alexandre
>
>
>
>
> On Oct 19, 2018, at 6:29 AM, Steffen Märcker <[hidden email]  
> <mailto:[hidden email]> > wrote:
>
> Nevermind, I figured it out easily. Must been blind before.
>
> Many thanks to the Iceberg team, the tool works like a charm in 6.1!
>
>
> Am .10.2018, 10:58 Uhr, schrieb Steffen Märcker <[hidden email]  
> <mailto:[hidden email]> >:
>
> <---Schnitt--->
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>



Reply | Threaded
Open this post in threaded view
|

Re: VW2Pharo ? (Was: Pharo2VW (Was:[vwnc] Parsing in Smalltalk))

Christian Haider
Yes, Resource Description Framework.
I wrote a RDF/XML parser/serializer and am quite excited about RDF - but have not done anything with it yet 😊
Pharo with Gemstone might be a good candidate for a triple store...

> -----Ursprüngliche Nachricht-----
> Von: Pharo-users <[hidden email]> Im Auftrag von
> Steffen Märcker
> Gesendet: Donnerstag, 15. November 2018 12:23
> An: [hidden email]
> Betreff: Re: [Pharo-users] VW2Pharo ? (Was: Pharo2VW (Was:[vwnc] Parsing
> in Smalltalk))
>
> Please let me know if I can help with that porting tool! Btw, is it RDF like
> Resource Description Framework?
>
> Dreamer mode: It would be awesome to teach VW tonel and Git for export
> and versioning!
>
> Best, Steffen
>
> Am .11.2018, 11:37 Uhr, schrieb Christian Haider
> <[hidden email]>:
>
> > Hi,
> >
> >
> > I did a tool for porting PDFtalk from VW to Gemstone (bundle {Gemstone
> > Fileout Project}) .
> >
> > When I have time, I plan to extend it for Pharo in order to port RDF
> > (and Values).
> >
> > I am thinking of making Pharo my RDF engine… we’ll see…
> >
> >
> > Happy hacking,
> >
> >                 Christian
> >
> >
> > Von: Cédrick Béler <[hidden email]>
> > Gesendet: Mittwoch, 14. November 2018 21:23
> > An: Any question about pharo is welcome <[hidden email]>
> > Cc: Christian Haider <[hidden email]>;
> > Christian Haider <[hidden email]>
> > Betreff: VW2Pharo ? (Was: Pharo2VW (Was:[vwnc] Parsing in Smalltalk))
> >
> >
> >
> > Objet: Rép : [Pharo-users] Pharo2VW (Was:[vwnc] Parsing in Smalltalk)
> >
> >
> > I really like the tool as it makes cross-platform-life a lot easier.
> >
> >
> > Thanks :-)
> >
> >
> >
> >
> > I really wish there was a similar tool for the reverse direction, too!
> >
> >
> > That is interesting. Anyone else interested in such a tool?
> >
> >
> >
> > A tool to port from VW to Pharo ?
> >
> >
> > Me interested, at least to port Christian work on RDF :)
> >
> >
> > Cheers,
> >
> >
> > Cédrick
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Cheers,
> > Alexandre
> >
> >
> >
> >
> >
> >
> > Cheers! Steffen
> >
> > Am .10.2018, 22:38 Uhr, schrieb Alexandre Bergel via Pharo-users
> > <[hidden email] <mailto:[hidden email]> >:
> >
> >
> >
> >
> > Thanks Steffen for your contribution to Pharo2VW.
> > We reviewed and accepted your PullRequests.
> >
> > Alexandre
> >
> >
> >
> >
> > On Oct 19, 2018, at 6:29 AM, Steffen Märcker <[hidden email]
> > <mailto:[hidden email]> > wrote:
> >
> > Nevermind, I figured it out easily. Must been blind before.
> >
> > Many thanks to the Iceberg team, the tool works like a charm in 6.1!
> >
> >
> > Am .10.2018, 10:58 Uhr, schrieb Steffen Märcker <[hidden email]
> > <mailto:[hidden email]> >:
> >
> > <---Schnitt--->
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>



Reply | Threaded
Open this post in threaded view
|

Re: VW2Pharo ? (Was: Pharo2VW (Was:[vwnc] Parsing in Smalltalk))

Esteban A. Maringolo
In reply to this post by Steffen Märcker
I did a lot of scripting to manually export Glorp from VW to Pharo,
using some of the available (and outdated) parcels for monticello. It
was painful and needed extra manual work at the file level, because of
the namespacing and the packaging characteristics of VW plus the
file-in complaints of Pharo compiler at that time.

A Tonel exporter would be way better, everything else feels more like
"rescuing" code from VW rather than exporting it.

This is something I'd like to collaborate, because I'm spending some
time with Seaside and VW and there are many library wrappers that I
could backport to Pharo and release them (e.g. like I did for
Bootstrap-Select).

Regards,


Esteban A. Maringolo
El jue., 15 nov. 2018 a las 8:23, Steffen Märcker (<[hidden email]>) escribió:

>
> Please let me know if I can help with that porting tool! Btw, is it RDF
> like Resource Description Framework?
>
> Dreamer mode: It would be awesome to teach VW tonel and Git for export and
> versioning!
>
> Best, Steffen
>
> Am .11.2018, 11:37 Uhr, schrieb Christian Haider
> <[hidden email]>:
>
> > Hi,
> >
> >
> > I did a tool for porting PDFtalk from VW to Gemstone (bundle {Gemstone
> > Fileout Project}) .
> >
> > When I have time, I plan to extend it for Pharo in order to port RDF
> > (and Values).
> >
> > I am thinking of making Pharo my RDF engine… we’ll see…
> >
> >
> > Happy hacking,
> >
> >                 Christian
> >
> >
> > Von: Cédrick Béler <[hidden email]>
> > Gesendet: Mittwoch, 14. November 2018 21:23
> > An: Any question about pharo is welcome <[hidden email]>
> > Cc: Christian Haider <[hidden email]>;
> > Christian Haider <[hidden email]>
> > Betreff: VW2Pharo ? (Was: Pharo2VW (Was:[vwnc] Parsing in Smalltalk))
> >
> >
> >
> > Objet: Rép : [Pharo-users] Pharo2VW (Was:[vwnc] Parsing in Smalltalk)
> >
> >
> > I really like the tool as it makes cross-platform-life a lot easier.
> >
> >
> > Thanks :-)
> >
> >
> >
> >
> > I really wish there was a similar tool for the reverse direction, too!
> >
> >
> > That is interesting. Anyone else interested in such a tool?
> >
> >
> >
> > A tool to port from VW to Pharo ?
> >
> >
> > Me interested, at least to port Christian work on RDF :)
> >
> >
> > Cheers,
> >
> >
> > Cédrick
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Cheers,
> > Alexandre
> >
> >
> >
> >
> >
> >
> > Cheers! Steffen
> >
> > Am .10.2018, 22:38 Uhr, schrieb Alexandre Bergel via Pharo-users
> > <[hidden email] <mailto:[hidden email]> >:
> >
> >
> >
> >
> > Thanks Steffen for your contribution to Pharo2VW.
> > We reviewed and accepted your PullRequests.
> >
> > Alexandre
> >
> >
> >
> >
> > On Oct 19, 2018, at 6:29 AM, Steffen Märcker <[hidden email]
> > <mailto:[hidden email]> > wrote:
> >
> > Nevermind, I figured it out easily. Must been blind before.
> >
> > Many thanks to the Iceberg team, the tool works like a charm in 6.1!
> >
> >
> > Am .10.2018, 10:58 Uhr, schrieb Steffen Märcker <[hidden email]
> > <mailto:[hidden email]> >:
> >
> > <---Schnitt--->
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: VW2Pharo ? (Was: Pharo2VW (Was:[vwnc] Parsing in Smalltalk))

Pharo Smalltalk Users mailing list
We put a significant amount of work into Pharo2VW
https://github.com/ObjectProfile/Pharo2VW

Let us know how useful is it for you.

Cheers,
Alexandre

> On Nov 15, 2018, at 9:36 AM, Esteban Maringolo <[hidden email]> wrote:
>
> I did a lot of scripting to manually export Glorp from VW to Pharo,
> using some of the available (and outdated) parcels for monticello. It
> was painful and needed extra manual work at the file level, because of
> the namespacing and the packaging characteristics of VW plus the
> file-in complaints of Pharo compiler at that time.
>
> A Tonel exporter would be way better, everything else feels more like
> "rescuing" code from VW rather than exporting it.
>
> This is something I'd like to collaborate, because I'm spending some
> time with Seaside and VW and there are many library wrappers that I
> could backport to Pharo and release them (e.g. like I did for
> Bootstrap-Select).
>
> Regards,
>
>
> Esteban A. Maringolo
> El jue., 15 nov. 2018 a las 8:23, Steffen Märcker (<[hidden email]>) escribió:
>>
>> Please let me know if I can help with that porting tool! Btw, is it RDF
>> like Resource Description Framework?
>>
>> Dreamer mode: It would be awesome to teach VW tonel and Git for export and
>> versioning!
>>
>> Best, Steffen
>>
>> Am .11.2018, 11:37 Uhr, schrieb Christian Haider
>> <[hidden email]>:
>>
>>> Hi,
>>>
>>>
>>> I did a tool for porting PDFtalk from VW to Gemstone (bundle {Gemstone
>>> Fileout Project}) .
>>>
>>> When I have time, I plan to extend it for Pharo in order to port RDF
>>> (and Values).
>>>
>>> I am thinking of making Pharo my RDF engine… we’ll see…
>>>
>>>
>>> Happy hacking,
>>>
>>>                Christian
>>>
>>>
>>> Von: Cédrick Béler <[hidden email]>
>>> Gesendet: Mittwoch, 14. November 2018 21:23
>>> An: Any question about pharo is welcome <[hidden email]>
>>> Cc: Christian Haider <[hidden email]>;
>>> Christian Haider <[hidden email]>
>>> Betreff: VW2Pharo ? (Was: Pharo2VW (Was:[vwnc] Parsing in Smalltalk))
>>>
>>>
>>>
>>> Objet: Rép : [Pharo-users] Pharo2VW (Was:[vwnc] Parsing in Smalltalk)
>>>
>>>
>>> I really like the tool as it makes cross-platform-life a lot easier.
>>>
>>>
>>> Thanks :-)
>>>
>>>
>>>
>>>
>>> I really wish there was a similar tool for the reverse direction, too!
>>>
>>>
>>> That is interesting. Anyone else interested in such a tool?
>>>
>>>
>>>
>>> A tool to port from VW to Pharo ?
>>>
>>>
>>> Me interested, at least to port Christian work on RDF :)
>>>
>>>
>>> Cheers,
>>>
>>>
>>> Cédrick
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Cheers,
>>> Alexandre
>>>
>>>
>>>
>>>
>>>
>>>
>>> Cheers! Steffen
>>>
>>> Am .10.2018, 22:38 Uhr, schrieb Alexandre Bergel via Pharo-users
>>> <[hidden email] <mailto:[hidden email]> >:
>>>
>>>
>>>
>>>
>>> Thanks Steffen for your contribution to Pharo2VW.
>>> We reviewed and accepted your PullRequests.
>>>
>>> Alexandre
>>>
>>>
>>>
>>>
>>> On Oct 19, 2018, at 6:29 AM, Steffen Märcker <[hidden email]
>>> <mailto:[hidden email]> > wrote:
>>>
>>> Nevermind, I figured it out easily. Must been blind before.
>>>
>>> Many thanks to the Iceberg team, the tool works like a charm in 6.1!
>>>
>>>
>>> Am .10.2018, 10:58 Uhr, schrieb Steffen Märcker <[hidden email]
>>> <mailto:[hidden email]> >:
>>>
>>> <---Schnitt--->
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>