Re: [Pharo-users] Seaside : including a static stylesheet.

[jtuc...@objektfabrik.de]

Hi Sabine,

this raises my interest. So you have two web servers listening to the 
same port, one being macOS X' built in web server (how did you 
activate/configure it?) and Seaside?


If I visit localhost:8080 on my mac (no pharo image or anything 
running), I get no answer, although there are files in 
/Library/WebServer/Documents (provided by Apple: index.html.en).


Joachim




Am 08.03.17 um 08:15 schrieb Sabine Manaa:

Hi Dominique,

try to use
http://localhost:8080/columnal.css
From your app
If you have your columlal.css
In
Library/WebServer/Documents/
Because
Library/WebServer/Documents
Is the web server root
This is the way I serve my static files

Regards
Sabine



Paul DeBruicker [via Smalltalk] <[hidden email] 
> schrieb am Mi. 8. 
März 2017 um 05:07:


Oh sorry.  I didn't edit my example above to your situation.  
Here try this:


1.  Open the seaside control panel and stop then remove all the
server adaptors.

2.  Put your directories & files next to your image.  So put your
'styles' folder next to your image.

3.  From the world menu open a Transcript.

4.  In a playground or workspace run:


|server|

ZnZincStaticServerAdaptor startOn: 8080 andServeFilesFrom:
FileSystem disk workingDirectory pathString.
server:=ZnZincStaticServerAdaptor default server.
server logToTranscript;
   debugMode: true.


I think that will get you a Zinc server serving static files from
the directory your image is in and will log everything to the
transcript and open a debugger when there is an error.






Dominique Dartois-4 wrote

Hi Sabine.

It does not seem working for me


I have found this directory here
"/Users/Dom/Documents/Library/WebServer/Documents" and I tried :

updateRoot: anHtmlRoot
super updateRoot: anHtmlRoot.
anHtmlRoot stylesheet url:
'http://localhost:8080/Library/WebServer/Documents/columnal.css'
.


The style sheet is not found.

I keep on trying.


Regards

---

Dominique



De : Pharo-users <[hidden email]
> de la
part de Sabine Manaa <[hidden email]
>

Envoyé : mardi 7 mars 2017 10:08:33
À : Any question about pharo is welcome
Objet : Re: [Pharo-users] Seaside : including a static
stylesheet.

Hi Dominique,

for some cases I also use static files on my local machine,
the root directory of the local machines web server is

/Library/WebServer/Documents

perhaps this is what you are looking for.

regards
Sabine

2017-02-28 18:53 GMT+01:00 Dominique Dartois <[hidden email]
>>:

In the Seaside book, chapter 17.2 I read I can include a
stylesheet this way :

updateRoot: anHtmlRoot
super updateRoot: anHtmlRoot.
anHtmlRoot stylesheet url:
'http://seaside.st/styles/main.css'


On my development machine (macOS) I use
http://localhost:8080/myApp as the server address and I don’t
know the root directory of the Seaside integrated web server.

Can anyone help me to find this directory?

Thanks.



---

Dominique Dartois

If you reply to this email, your message will be added to the
discussion below:

http://forum.world.st/Seaside-including-a-static-stylesheet-tp4936435p4937841.html

To start a new topic under Pharo Smalltalk Users, email [hidden
email] 
To unsubscribe from Pharo Smalltalk Users, click here.
NAML






View this message in context: Re: Seaside : including a static 
stylesheet. 

Sent from the Pharo Smalltalk Users mailing list archive 
 at Nabble.com.



--
---
Objektfabrik Joachim Tuchel  mailto:jtuc...@objektfabrik.de
Fliederweg 1 http://www.objektfabrik.de
D-71640 Ludwigsburg  

Re: [Pharo-users] couchdb integration?

[stepharong]

Re: [Pharo-users] Pharo Spur 64 VM

[stepharong]

Re: [Pharo-users] Seaside : including a static stylesheet.

[Sabine Manaa]

Dominique,

you could test that with putting a simple html file there, e.g. index.html
and than visit with your browser

http://localhost/index.html

than this file should be shown.

This has nothing to do with seaside, it is only about finding the web
server root on mac.
Perhaps Pauls solution is better.

Regards
Sabine

2017-03-08 8:15 GMT+01:00 Sabine Manaa :

> Hi Dominique,
>
> try to use
> http://localhost:8080/columnal.css
> From your app
> If you have your columlal.css
> In
> Library/WebServer/Documents/
> Because
> Library/WebServer/Documents
> Is the web server root
> This is the way I serve my static files
>
> Regards
> Sabine
>
>
>
> Paul DeBruicker [via Smalltalk] <[hidden email]
> > schrieb am Mi.
> 8. März 2017 um 05:07:
>
>> Oh sorry.  I didn't edit my example above to your situation.   Here try
>> this:
>>
>> 1.  Open the seaside control panel and stop then remove all the server
>> adaptors.
>>
>> 2.  Put your directories & files next to your image.  So put your
>> 'styles' folder next to your image.
>>
>> 3.  From the world menu open a Transcript.
>>
>> 4.  In a playground or workspace run:
>>
>>
>> |server|
>>
>> ZnZincStaticServerAdaptor startOn: 8080 andServeFilesFrom: FileSystem
>> disk workingDirectory pathString.
>> server:=ZnZincStaticServerAdaptor default server.
>> server logToTranscript;
>>debugMode: true.
>>
>>
>> I think that will get you a Zinc server serving static files from the
>> directory your image is in and will log everything to the transcript and
>> open a debugger when there is an error.
>>
>>
>>
>>
>>
>>
>> Dominique Dartois-4 wrote
>>
>> Hi Sabine.
>>
>> It does not seem working for me
>>
>>
>> I have found this directory here 
>> "/Users/Dom/Documents/Library/WebServer/Documents"
>> and I tried :
>>
>> updateRoot: anHtmlRoot
>> super updateRoot: anHtmlRoot.
>> anHtmlRoot stylesheet url: 'http://localhost:8080/
>> Library/WebServer/Documents/columnal.css'.
>>
>> The style sheet is not found.
>>
>> I keep on trying.
>>
>>
>> Regards
>>
>> ---
>>
>> Dominique
>>
>> 
>>
>> De : Pharo-users <[hidden email]
>> > de la part de
>> Sabine Manaa <[hidden email]
>> >
>>
>> Envoyé : mardi 7 mars 2017 10:08:33
>> À : Any question about pharo is welcome
>> Objet : Re: [Pharo-users] Seaside : including a static stylesheet.
>>
>> Hi Dominique,
>>
>> for some cases I also use static files on my local machine, the root
>> directory of the local machines web server is
>>
>> /Library/WebServer/Documents
>>
>> perhaps this is what you are looking for.
>>
>> regards
>> Sabine
>>
>> 2017-02-28 18:53 GMT+01:00 Dominique Dartois <[hidden email]
>> > email] >>:
>>
>> In the Seaside book, chapter 17.2 I read I can include a stylesheet this
>> way :
>>
>> updateRoot: anHtmlRoot
>> super updateRoot: anHtmlRoot.
>> anHtmlRoot stylesheet url: 'http://seaside.st/styles/main.css'
>>
>> On my development machine (macOS) I use http://localhost:8080/myApp as
>> the server address and I don’t know the root directory of the Seaside
>> integrated web server.
>>
>> Can anyone help me to find this directory?
>>
>> Thanks.
>>
>>
>>
>> ---
>>
>> Dominique Dartois
>>
>> If you reply to this email, your message will be added to the discussion
>> below:
>> http://forum.world.st/Seaside-including-a-static-stylesheet-
>> tp4936435p4937841.html
>> To start a new topic under Pharo Smalltalk Users, email [hidden email]
>> 
>> To unsubscribe from Pharo Smalltalk Users, click here.
>> NAML
>> 
>>
>
> --
> View this message in context: Re: Seaside : including a static stylesheet.
> 
> Sent from the Pharo Smalltalk Users mailing list archive
>  at Nabble.com.
>

Re: [Pharo-users] Seaside : including a static stylesheet.

[Sabine Manaa]

Hi Dominique,

try to use
http://localhost:8080/columnal.css
>From your app
If you have your columlal.css
In
Library/WebServer/Documents/
Because
Library/WebServer/Documents
Is the web server root
This is the way I serve my static files

Regards
Sabine



Paul DeBruicker [via Smalltalk] 
schrieb am Mi. 8. März 2017 um 05:07:

> Oh sorry.  I didn't edit my example above to your situation.   Here try
> this:
>
> 1.  Open the seaside control panel and stop then remove all the server
> adaptors.
>
> 2.  Put your directories & files next to your image.  So put your 'styles'
> folder next to your image.
>
> 3.  From the world menu open a Transcript.
>
> 4.  In a playground or workspace run:
>
>
> |server|
>
> ZnZincStaticServerAdaptor startOn: 8080 andServeFilesFrom: FileSystem disk
> workingDirectory pathString.
> server:=ZnZincStaticServerAdaptor default server.
> server logToTranscript;
>debugMode: true.
>
>
> I think that will get you a Zinc server serving static files from the
> directory your image is in and will log everything to the transcript and
> open a debugger when there is an error.
>
>
>
>
>
>
> Dominique Dartois-4 wrote
>
> Hi Sabine.
>
> It does not seem working for me
>
>
> I have found this directory here
> "/Users/Dom/Documents/Library/WebServer/Documents" and I tried :
>
> updateRoot: anHtmlRoot
> super updateRoot: anHtmlRoot.
> anHtmlRoot stylesheet url: '
> http://localhost:8080/Library/WebServer/Documents/columnal.css'.
>
> The style sheet is not found.
>
> I keep on trying.
>
>
> Regards
>
> ---
>
> Dominique
>
> 
>
> De : Pharo-users <[hidden email]
> > de la part de
> Sabine Manaa <[hidden email]
> >
>
> Envoyé : mardi 7 mars 2017 10:08:33
> À : Any question about pharo is welcome
> Objet : Re: [Pharo-users] Seaside : including a static stylesheet.
>
> Hi Dominique,
>
> for some cases I also use static files on my local machine, the root
> directory of the local machines web server is
>
> /Library/WebServer/Documents
>
> perhaps this is what you are looking for.
>
> regards
> Sabine
>
> 2017-02-28 18:53 GMT+01:00 Dominique Dartois <[hidden email]
>  email] >>:
>
> In the Seaside book, chapter 17.2 I read I can include a stylesheet this
> way :
>
> updateRoot: anHtmlRoot
> super updateRoot: anHtmlRoot.
> anHtmlRoot stylesheet url: 'http://seaside.st/styles/main.css'
>
> On my development machine (macOS) I use http://localhost:8080/myApp as
> the server address and I don’t know the root directory of the Seaside
> integrated web server.
>
> Can anyone help me to find this directory?
>
> Thanks.
>
>
>
> ---
>
> Dominique Dartois
>
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://forum.world.st/Seaside-including-a-static-stylesheet-tp4936435p4937841.html
> To start a new topic under Pharo Smalltalk Users, email
> ml-node+s1294792n1310670...@n4.nabble.com
> To unsubscribe from Pharo Smalltalk Users, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://forum.world.st/Seaside-including-a-static-stylesheet-tp4936435p4937845.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

[Pharo-users] [ANN] Student Membership level Pharo Association

[Marcus Denker]

Hi,

We added this some time ago, but never announced it:

There is now a “Student” memership level for the Pharo Association. This
gives a 50% discount compared to the standard membership.

Join here:

https://association.pharo.org/join-us 



Marcus

Re: [Pharo-users] Seaside : including a static stylesheet.

[Paul DeBruicker]

Oh sorry.  I didn't edit my example above to your situation.   Here try this:

1.  Open the seaside control panel and stop then remove all the server
adaptors.

2.  Put your directories & files next to your image.  So put your 'styles'
folder next to your image.

3.  From the world menu open a Transcript.

4.  In a playground or workspace run:


|server|

ZnZincStaticServerAdaptor startOn: 8080 andServeFilesFrom: FileSystem disk
workingDirectory pathString. 
server:=ZnZincStaticServerAdaptor default server.
server logToTranscript; 
   debugMode: true.


I think that will get you a Zinc server serving static files from the
directory your image is in and will log everything to the transcript and
open a debugger when there is an error.  







Dominique Dartois-4 wrote
> Hi Sabine.
> 
> It does not seem working for me
> 
> 
> I have found this directory here
> "/Users/Dom/Documents/Library/WebServer/Documents" and I tried :
> 
> updateRoot: anHtmlRoot
> super updateRoot: anHtmlRoot.
> anHtmlRoot stylesheet url:
> 'http://localhost:8080/Library/WebServer/Documents/columnal.css'.
> 
> The style sheet is not found.
> 
> I keep on trying.
> 
> 
> Regards
> 
> ---
> 
> Dominique
> 
> 
> De : Pharo-users 

> pharo-users-bounces@.pharo

>  de la part de Sabine Manaa 

> manaa.sabine@

> 
> Envoyé : mardi 7 mars 2017 10:08:33
> À : Any question about pharo is welcome
> Objet : Re: [Pharo-users] Seaside : including a static stylesheet.
> 
> Hi Dominique,
> 
> for some cases I also use static files on my local machine, the root
> directory of the local machines web server is
> 
> /Library/WebServer/Documents
> 
> perhaps this is what you are looking for.
> 
> regards
> Sabine
> 
> 2017-02-28 18:53 GMT+01:00 Dominique Dartois 

> dom@

> mailto:

> dom@

> >:
> In the Seaside book, chapter 17.2 I read I can include a stylesheet this
> way :
> 
> updateRoot: anHtmlRoot
> super updateRoot: anHtmlRoot.
> anHtmlRoot stylesheet url: 'http://seaside.st/styles/main.css'
> 
> On my development machine (macOS) I use http://localhost:8080/myApp as the
> server address and I don’t know the root directory of the Seaside
> integrated web server.
> 
> Can anyone help me to find this directory?
> 
> Thanks.
> 
> 
> 
> ---
> 
> Dominique Dartois





--
View this message in context: 
http://forum.world.st/Seaside-including-a-static-stylesheet-tp4936435p4937841.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Seaside : including a static stylesheet.

[Dominique Dartois]

Hi Sabine.

It does not seem working for me


I have found this directory here 
"/Users/Dom/Documents/Library/WebServer/Documents" and I tried :

updateRoot: anHtmlRoot
super updateRoot: anHtmlRoot.
anHtmlRoot stylesheet url: 
'http://localhost:8080/Library/WebServer/Documents/columnal.css'.

The style sheet is not found.

I keep on trying.


Regards

---

Dominique


De : Pharo-users  de la part de Sabine 
Manaa 
Envoyé : mardi 7 mars 2017 10:08:33
À : Any question about pharo is welcome
Objet : Re: [Pharo-users] Seaside : including a static stylesheet.

Hi Dominique,

for some cases I also use static files on my local machine, the root directory 
of the local machines web server is

/Library/WebServer/Documents

perhaps this is what you are looking for.

regards
Sabine

2017-02-28 18:53 GMT+01:00 Dominique Dartois 
>:
In the Seaside book, chapter 17.2 I read I can include a stylesheet this way :

updateRoot: anHtmlRoot
super updateRoot: anHtmlRoot.
anHtmlRoot stylesheet url: 'http://seaside.st/styles/main.css'

On my development machine (macOS) I use http://localhost:8080/myApp as the 
server address and I don’t know the root directory of the Seaside integrated 
web server.

Can anyone help me to find this directory?

Thanks.



---

Dominique Dartois

Re: [Pharo-users] Pharo Spur 64 VM

[stepharong]

Re: [Pharo-users] Pharo Spur 64 VM

[stepharong]

Re: [Pharo-users] Pharo Spur 64 VM

[Hernán Morales Durand]

I am learning a lot about this (raising money).

Now if someone wants to work together to get funding (for
developing/updating the Windows VM) please let me know so we can evaluate
alternatives.

Hernán


2017-03-07 15:24 GMT-03:00 stepharong :

> Yes we know that we should improve the windows part.
> We agree. Now I do not know how to create money.
>
> Stef
>
> Just asking,
>
> Did someone already tried to get funding to update the Windows VM?
> Because it's like the 90% of the world still uses Windows...
>
> Regards,
>
> Hernán
>
>
>
> 2017-03-02 12:51 GMT-03:00 Clément Bera :
>
>> Hi Raffaello,
>>
>> Reportedly, the VM without the JIT (pure interpreter, also called PharoS
>> or StackVM) works on windows 64 and FFI works with it if the VM compiled
>> with clang but not with gcc. There is no configuration for Pharo right now.
>> It should not be hard to add a pharo configuration to have the image
>> start-up, but I don't think several libraries such as Athens/Cairo or
>> libgit would work out of the box, so it's not clear such a configuration
>> would make a lot of sense. There is no PharoS-spur64 repository on
>> files.pharo.org right now either.
>>
>> Windows support is not ready mostly because:
>> - Some C types are different in x64 between Unix and windows
>> - Calling conventions are different in x64 bits between Unix and Windows
>>
>> Calling conventions have impact in switching between the interpreter and
>> the JIT runtime and in FFI.
>> C types being different have impact for the VM compilation and in FFI.
>>
>> If someone looks into it, I guess in a day of work we could have the
>> Stack VM working with Spur 64 for Pharo without support for some
>> librairies. There might be uncommon crashes to fix over the first week of
>> use. With several more weeks of work (maybe a couple months), the StackVM
>> with all libraries should be production-ready. The JIT support will take
>> more time, hopefully it will be done in a year from now.
>>
>> Maybe I should mention that the company who funded 64 bits support is
>> using the VM on Mac for development and Linux for production, so Windows
>> was not a priority and not done. We have to rely on open-source
>> contributors, non paid, to add Windows support and that takes time. Nicolas
>> Cellier added the support for the 64 bits Stack VM on his free time. If
>> someone is investing money, the 64 bits Windows VM could reach production
>> sooner (I guess within 6 months) because someone could work full time on it.
>>
>> Regards,
>>
>>
>> On Thu, Mar 2, 2017 at 4:04 PM,  wrote:
>>
>>> On 07/02/17 07:13, Esteban Lorenzano wrote:
>>> >
>>> >> On 6 Feb 2017, at 21:41, Cyril Ferlicot D. 
>>> wrote:
>>> >>
>>> >> Le 06/02/2017 à 21:31, Benoit St-Jean via Pharo-users a écrit :
>>> >>
>>> >>
>>> >> Hi!
>>> >>
>>> >> IIRC, the windows VM will need some more time to be ready. Only Linux
>>> >> and OSX ones are usable at the moment.
>>> >
>>> > ^ this.
>>> > as Cyril says, win 64bits vm is still not ready (and it will take some
>>> more time to be).
>>> >
>>> > Esteban
>>> >
>>>
>>>
>>> Just for general curiosity, what are the main stumbling blocks in the
>>> road to a Windows 64 bit Pharo?
>>>
>>>
>>> Raffaello
>>>
>>>
>>>
>>
>
>
>
> --
> Using Opera's mail client: http://www.opera.com/mail/
>

Re: [Pharo-users] couchdb integration?

[stepharong]

Yes there was a package Igor did one long time ago.




Hi,

Does anyone know if there any CouchDB integration in Pharo?

For example, I would be interested if there is any Pharo implementation  
for the CouchDB Replication Protocol:

http://docs.couchdb.org/en/master/replication/protocol.html

Cheers,
Doru


--
www.tudorgirba.com
www.feenk.com

"In a world where everything is moving ever faster,
one might have better chances to win by moving slower."








--
Using Opera's mail client: http://www.opera.com/mail/

Re: [Pharo-users] Pharo Spur 64 VM

[stepharong]

Yes we know that we should improve the windows part.
We agree. Now I do not know how to create money.

Stef


Just asking,

Did someone already tried to get funding to update the Windows VM?
Because it's like the 90% of the world still uses Windows...

Regards,

Hernán



2017-03-02 12:51 GMT-03:00 Clément Bera :

Hi Raffaello,

Reportedly, the VM without the JIT (pure interpreter, also called  
PharoS or StackVM) works on windows 64 and FFI works with it if the VM  
compiled with clang but not with gcc. >>There is no configuration for  
Pharo right now. It should not be hard to add a pharo configuration to  
have the image start-up, but I don't think several libraries such as  
Athens/>>Cairo or libgit would work out of the box, so it's not clear  
such a configuration would make a lot of sense. There is no  
PharoS-spur64 repository on files.pharo.org right now >>either.

Windows support is not ready mostly because:
- Some C types are different in x64 between Unix and windows
- Calling conventions are different in x64 bits between Unix and Windows

Calling conventions have impact in switching between the interpreter  
and the JIT runtime and in FFI.

C types being different have impact for the VM compilation and in FFI.

If someone looks into it, I guess in a day of work we could have the  
Stack VM working with Spur 64 for Pharo without support for some  
librairies. There might be uncommon >>crashes to fix over the first  
week of use. With several more weeks of work (maybe a couple months),  
the StackVM with all libraries should be production-ready. The JIT  
support >>will take more time, hopefully it will be done in a year from  
now.


Maybe I should mention that the company who funded 64 bits support is  
using the VM on Mac for development and Linux for production, so  
Windows was not a priority and >>not done. We have to rely on  
open-source contributors, non paid, to add Windows support and that  
takes time. Nicolas Cellier added the support for the 64 bits Stack VM  
on >>his free time. If someone is investing money, the 64 bits Windows  
VM could reach production sooner (I guess within 6 months) because  
someone could work full time on it.


Regards,

On Thu, Mar 2, 2017 at 4:04 PM,  wrote:

On 07/02/17 07:13, Esteban Lorenzano wrote:


On 6 Feb 2017, at 21:41, Cyril Ferlicot D.  
 wrote:


Le 06/02/2017 à 21:31, Benoit St-Jean via Pharo-users a écrit :


Hi!

IIRC, the windows VM will need some more time to be ready. Only Linux
and OSX ones are usable at the moment.


^ this.
as Cyril says, win 64bits vm is still not ready (and it will take  
some more time to be).


Esteban




Just for general curiosity, what are the main stumbling blocks in the
road to a Windows 64 bit Pharo?


Raffaello










--
Using Opera's mail client: http://www.opera.com/mail/

Re: [Pharo-users] Convert Markdown to Pillar?

[Dimitris Chloupis]

Well the simplest way is to write it markdown and then use a converter like
Pandadoc to convert markdown to latex. You can inline latex in Pillar if
you want to convert Latex to Pillar you will have to use an emacs mode that
Damien made that converts Latex to Pillar. I have converted a ton of Latex
to Pillar with the emacs mode that saved me a ton of time when I was
porting PBE to Pharo 4 and to pillar (original PBE was completely written
in Latex).

On Tue, Mar 7, 2017 at 6:56 PM sergio ruiz  wrote:

>
> Just wondering if this is possible. Just about every stand alone editor
> allows users to edit or export to markdown. I tend to do everything in a
> standalone editor when getting written material ready for publishing to the
> web.
>
> I don’t have any beef with pillar, i just want to be able to write using a
> separate tool.
>
> thanks!
>
>
> 
> peace,
> sergio
> photographer, journalist, visionary
>
> Public Key: http://bit.ly/29z9fG0
> #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
> http://www.Village-Buzz.com
> http://www.ThoseOptimizeGuys.com
> http://www.coffee-black.com
> http://www.painlessfrugality.com
> http://www.twitter.com/sergio_101
> http://www.facebook.com/sergio101
>

Re: [Pharo-users] Convert Markdown to Pillar?

[Damien Pollet]

Should be possible, but that would involve writing a markdown to pillar
converter :)

The other way around already exists, but the conversion is lossy; from
markdown to pillar it should be possible to maintain most of the semantics.


On 7 March 2017 at 17:55, sergio ruiz  wrote:

>
> Just wondering if this is possible. Just about every stand alone editor
> allows users to edit or export to markdown. I tend to do everything in a
> standalone editor when getting written material ready for publishing to the
> web.
>
> I don’t have any beef with pillar, i just want to be able to write using a
> separate tool.
>
> thanks!
>
>
> 
> peace,
> sergio
> photographer, journalist, visionary
>
> Public Key: http://bit.ly/29z9fG0
> #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
> http://www.Village-Buzz.com
> http://www.ThoseOptimizeGuys.com
> http://www.coffee-black.com
> http://www.painlessfrugality.com
> http://www.twitter.com/sergio_101
> http://www.facebook.com/sergio101
>

[Pharo-users] Convert Markdown to Pillar?

[sergio ruiz]

Just wondering if this is possible. Just about every stand alone editor allows 
users to edit or export to markdown. I tend to do everything in a standalone 
editor when getting written material ready for publishing to the web.

I don’t have any beef with pillar, i just want to be able to write using a 
separate tool.

thanks!



peace,
sergio
photographer, journalist, visionary

Public Key: http://bit.ly/29z9fG0
#BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
http://www.Village-Buzz.com
http://www.ThoseOptimizeGuys.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101

signature.asc
Description: Message signed with OpenPGP using AMPGpg

Re: [Pharo-users] [State Machine] Looking for some examples.

[sergio ruiz]

Oh.. that looks like a good call! 

thanks!



On March 7, 2017 at 12:21:12 AM, Hernán Morales Durand 
(hernan.mora...@gmail.com) wrote:

I never used StateMachine, but a really cool package with some examples is 
SState:

http://www.smalltalkhub.com/#!/~MasashiUmezawa/SState

Cheers,

Hernán


2017-03-07 1:14 GMT-03:00 sergio ruiz :
Hey, all..

Just wondering if anyone had any resources for examples of using StateMachine 
package in Pharo. 

I am looking at it, and looked at the tests, but am not finding a really clear 
example on how this works.

Ideas?

Thanks!



peace,
sergio
photographer, journalist, visionary

Public Key: http://bit.ly/29z9fG0
#BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
http://www.Village-Buzz.com
http://www.ThoseOptimizeGuys.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101


peace,
sergio
photographer, journalist, visionary

Public Key: http://bit.ly/29z9fG0
#BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV
http://www.Village-Buzz.com
http://www.ThoseOptimizeGuys.com
http://www.coffee-black.com
http://www.painlessfrugality.com
http://www.twitter.com/sergio_101
http://www.facebook.com/sergio101

signature.asc
Description: Message signed with OpenPGP using AMPGpg

Re: [Pharo-users] Voyage and instances retrieving

[Hilaire]

I'll make a test case to illustrate the issue.

Hilaire

Le 06/03/2017 à 19:05, Esteban Lorenzano a écrit :
>> Ah, sorry I was not clear enough in my introduction. Obviously, I
>> removed all =/hash overrides on the involved objects and it is therefore
>> an orthogonal issue (that's why I first resolved the other issues
>> first). Or did you mean something I did not understand in your previous
>> message?
> no, I didn’t understood you removed #= and #hash :)
> 

-- 
Dr. Geo
http://drgeo.eu

Re: [Pharo-users] Pharo Spur 64 VM

[Raffaello Giulietti]

My guess is, yes, while 90% of the desktops still run Windows, probably 
most of the developers related to Pharo use macOS. And since macOS is 
similar to Linux, porting to Linux is easy while porting to Windows 
seems not for the reasons outlined by Clément.




On 2017-03-07 04:58, Hernán Morales Durand wrote:

Just asking,

Did someone already tried to get funding to update the Windows VM?
Because it's like the 90% of the world still uses Windows...

Regards,

Hernán



2017-03-02 12:51 GMT-03:00 Clément Bera >:


Hi Raffaello,

Reportedly, the VM without the JIT (pure interpreter, also called
PharoS or StackVM) works on windows 64 and FFI works with it if
the VM compiled with clang but not with gcc. There is no
configuration for Pharo right now. It should not be hard to add a
pharo configuration to have the image start-up, but I don't think
several libraries such as Athens/Cairo or libgit would work out of
the box, so it's not clear such a configuration would make a lot
of sense. There is no PharoS-spur64 repository on files.pharo.org
 right now either.

Windows support is not ready mostly because:
- Some C types are different in x64 between Unix and windows
- Calling conventions are different in x64 bits between Unix and
Windows

Calling conventions have impact in switching between the
interpreter and the JIT runtime and in FFI.
C types being different have impact for the VM compilation and in FFI.

If someone looks into it, I guess in a day of work we could have
the Stack VM working with Spur 64 for Pharo without support for
some librairies. There might be uncommon crashes to fix over the
first week of use. With several more weeks of work (maybe a couple
months), the StackVM with all libraries should be
production-ready. The JIT support will take more time, hopefully
it will be done in a year from now.

Maybe I should mention that the company who funded 64 bits support
is using the VM on Mac for development and Linux for production,
so Windows was not a priority and not done. We have to rely on
open-source contributors, non paid, to add Windows support and
that takes time. Nicolas Cellier added the support for the 64 bits
Stack VM on his free time. If someone is investing money, the 64
bits Windows VM could reach production sooner (I guess within 6
months) because someone could work full time on it.

Regards,

On Thu, Mar 2, 2017 at 4:04 PM, > wrote:

On 07/02/17 07:13, Esteban Lorenzano wrote:
>
>> On 6 Feb 2017, at 21:41, Cyril Ferlicot D.
>
wrote:
>>
>> Le 06/02/2017 à 21:31, Benoit St-Jean via Pharo-users a écrit :
>>
>>
>> Hi!
>>
>> IIRC, the windows VM will need some more time to be ready.
Only Linux
>> and OSX ones are usable at the moment.
>
> ^ this.
> as Cyril says, win 64bits vm is still not ready (and it will
take some more time to be).
>
> Esteban
>


Just for general curiosity, what are the main stumbling blocks
in the
road to a Windows 64 bit Pharo?


Raffaello

Re: [Pharo-users] Pharo Association

[denker]

> On 1 Mar 2017, at 18:29, Jimmie Houchin  wrote:
> 
> Hello, I am looking into the Pharo Association.
> 
> I looked at the Contribute page, http://pharo.org/contribute  and saw the 
> links to BountySource.
> 
> One of them had $9 monthly being a Gold Membership Pharo Association. I do 
> not see this as an option if you do Join on the Pharo Association Join Us 
> page, https://association.pharo.org/join-us .
> 

Yes.

Integrating salt there would be very complex. For one, we do not get any 
email/information from Salt about new members.
So this is manual: it is one form of payment. (like money transfer). 

> I do not know which option is most favorable for or least expensive to the 
> Pharo Association.
> 
Direct membership. Bountisource costs 10%.


> I also do not see what payment methods are available on the Pharo Association 
> pages. BountySource I know my options.
> 
> From the BountySource page I do not know how this connects me to the 
> PharoAssociation.
> 
Not directly as they do not tell us when a new person subscribes.

> If all things are equal, I would assume do BountySource, I can start a 
> monthly cash flow immediately.
> 
> It would also be nice to know if doing BountySource that is always an option 
> to levels other than the set levels but you only get the benefits of the 
> highest level you contribute at.
> 
> For example if I wanted to do $15 a month instead of $9, or even a simply $10 
> instead of $9. or ….


Sadly we can not change the despriptions at SALT. I did send a mail to support 
but never got an answer.

> I think this could be by instead of saying $9 a month, express it as minimum 
> of $9 a month. Or what is appropriate for each level.
> 
> If BountySource is more expensive on the Association's end. I would prefer to 
> do whatever payment options are on the Association site. But it would be nice 
> to know what those are before I begin to complete the forms.
> 

Best is to go directly via the association. Espeically that Salt 
- does not tell us new sponsors
- does not respond to suport requests
- takes 10% for that

Marcus

Re: [Pharo-users] Seaside : including a static stylesheet.

[Sabine Manaa]

Hi Dominique,

for some cases I also use static files on my local machine, the root
directory of the local machines web server is

/Library/WebServer/Documents

perhaps this is what you are looking for.

regards
Sabine

2017-02-28 18:53 GMT+01:00 Dominique Dartois :

> In the Seaside book, chapter 17.2 I read I can include a stylesheet this
> way :
>
> updateRoot: anHtmlRoot
> super updateRoot: anHtmlRoot.
> anHtmlRoot stylesheet url: 'http://seaside.st/styles/main.css'
>
> On my development machine (macOS) I use http://localhost:8080/myApp as
> the server address and I don’t know the root directory of the Seaside
> integrated web server.
>
> Can anyone help me to find this directory?
>
> Thanks.
>
>
>
> ---
>
> Dominique Dartois
>