Humanised haxelib (patch)

classic Classic list List threaded Threaded
20 messages Options
Reply | Threaded
Open this post in threaded view
|

Humanised haxelib (patch)

Pimm Hogeling
Hi list,

Having a RubyGems-like application for haXe is awesome. I love haxelib. My team uses it constantly. However, (luckily) not every haXe developer out there is as digitally-minded as Nicolas, which is why I feel the haxelib client is too "technical".

I've spent an hour or two making modifications to the interface of the haxelib client. The result is attached, as well as two before-and-after screenshots that demonstrate some of the changes.

Feedback welcome - as always!

--
haXe - an open source web programming language
http://haxe.org

Humanised haxelib.patch (38K) Download Attachment
Screenshot 1 old.png (16K) Download Attachment
Screenshot 1 new.png (21K) Download Attachment
Screenshot 2 old.png (1K) Download Attachment
Screenshot 2 new.png (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

basvanmeurs
I agree that the haxelib interface could be more user-friendly. Your modifications are indeed an improvement, but just a minor. Personally I think that we should search the solution in a little GUI that uses the CLI. This doesn't necessarily have to be written in HaXe. It could provide a good overview of the installed packages, whether or not it is up to date, etc.
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Nicolas Cannasse
Le 12/03/2011 13:34, basvanmeurs a écrit :
> I agree that the haxelib interface could be more user-friendly. Your
> modifications are indeed an improvement, but just a minor. Personally I
> think that we should search the solution in a little GUI that uses the CLI.
> This doesn't necessarily have to be written in HaXe. It could provide a good
> overview of the installed packages, whether or not it is up to date, etc.

+1 for an haxelib UI. It can actually connect directly to the haxelib
server without calling the haxelib commandline since it's based on haxe
remoting.

Nicolas

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Pimm Hogeling
On the other hand, a client with CLI is more flexible. It can be used by an IDE, for instance. Plus a CLI can be just as user-friendly as a GUI.

On 12 March 2011 17:41, Nicolas Cannasse <[hidden email]> wrote:
Le 12/03/2011 13:34, basvanmeurs a écrit :

I agree that the haxelib interface could be more user-friendly. Your
modifications are indeed an improvement, but just a minor. Personally I
think that we should search the solution in a little GUI that uses the CLI.
This doesn't necessarily have to be written in HaXe. It could provide a good
overview of the installed packages, whether or not it is up to date, etc.

+1 for an haxelib UI. It can actually connect directly to the haxelib server without calling the haxelib commandline since it's based on haxe remoting.

Nicolas


--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Franco Ponticelli
They can both coexist without having to worry too much and visual tools have a bigger impacts on new users.

Franco

On Sat, Mar 12, 2011 at 5:11 PM, Pimm Hogeling <[hidden email]> wrote:
On the other hand, a client with CLI is more flexible. It can be used by an IDE, for instance. Plus a CLI can be just as user-friendly as a GUI.


On 12 March 2011 17:41, Nicolas Cannasse <[hidden email]> wrote:
Le 12/03/2011 13:34, basvanmeurs a écrit :

I agree that the haxelib interface could be more user-friendly. Your
modifications are indeed an improvement, but just a minor. Personally I
think that we should search the solution in a little GUI that uses the CLI.
This doesn't necessarily have to be written in HaXe. It could provide a good
overview of the installed packages, whether or not it is up to date, etc.

+1 for an haxelib UI. It can actually connect directly to the haxelib server without calling the haxelib commandline since it's based on haxe remoting.

Nicolas


--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Tony Polinelli
Caue is working on the C# target - apparantly quite close. So i guess this would makw a CLI interface with remoting in the backend, a breeze!

On Sun, Mar 13, 2011 at 4:55 AM, Franco Ponticelli <[hidden email]> wrote:
They can both coexist without having to worry too much and visual tools have a bigger impacts on new users.

Franco

On Sat, Mar 12, 2011 at 5:11 PM, Pimm Hogeling <[hidden email]> wrote:
On the other hand, a client with CLI is more flexible. It can be used by an IDE, for instance. Plus a CLI can be just as user-friendly as a GUI.


On 12 March 2011 17:41, Nicolas Cannasse <[hidden email]> wrote:
Le 12/03/2011 13:34, basvanmeurs a écrit :

I agree that the haxelib interface could be more user-friendly. Your
modifications are indeed an improvement, but just a minor. Personally I
think that we should search the solution in a little GUI that uses the CLI.
This doesn't necessarily have to be written in HaXe. It could provide a good
overview of the installed packages, whether or not it is up to date, etc.

+1 for an haxelib UI. It can actually connect directly to the haxelib server without calling the haxelib commandline since it's based on haxe remoting.

Nicolas


--
haXe - an open source web programming language
http://haxe.org


--

haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org



--
Tony Polinelli
http://touchmypixel.com

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Justin Donaldson-3
In reply to this post by Pimm Hogeling
It would be nice if the CLI got a little more love.  I'm doing more and more work on remote terminals these days.

-Justin

On Sat, Mar 12, 2011 at 9:11 AM, Pimm Hogeling <[hidden email]> wrote:
On the other hand, a client with CLI is more flexible. It can be used by an IDE, for instance. Plus a CLI can be just as user-friendly as a GUI.


On 12 March 2011 17:41, Nicolas Cannasse <[hidden email]> wrote:
Le 12/03/2011 13:34, basvanmeurs a écrit :

I agree that the haxelib interface could be more user-friendly. Your
modifications are indeed an improvement, but just a minor. Personally I
think that we should search the solution in a little GUI that uses the CLI.
This doesn't necessarily have to be written in HaXe. It could provide a good
overview of the installed packages, whether or not it is up to date, etc.

+1 for an haxelib UI. It can actually connect directly to the haxelib server without calling the haxelib commandline since it's based on haxe remoting.

Nicolas


--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Tarwin Stroh-Spijer
In reply to this post by Tony Polinelli
I'm giving a +1, but really think it would be best to write it in haxe, even if it may be a little more work to get a UI. Why not do it as an AIR app, that'd make easy UI and easy cross platform.

It's good for the community for people who are picking up the language to be able to edit the tools in that same language. (sometimes I lament that we don't have a haxe haxe compiler, but I totally understand why).


Tarwin Stroh-Spijer
_______________________

Touch My Pixel
http://www.touchmypixel.com/
phone: +61 3 8060 5321
_______________________


On Sun, Mar 13, 2011 at 8:53 AM, Tony Polinelli <[hidden email]> wrote:
Caue is working on the C# target - apparantly quite close. So i guess this would makw a CLI interface with remoting in the backend, a breeze!

On Sun, Mar 13, 2011 at 4:55 AM, Franco Ponticelli <[hidden email]> wrote:
They can both coexist without having to worry too much and visual tools have a bigger impacts on new users.

Franco

On Sat, Mar 12, 2011 at 5:11 PM, Pimm Hogeling <[hidden email]> wrote:
On the other hand, a client with CLI is more flexible. It can be used by an IDE, for instance. Plus a CLI can be just as user-friendly as a GUI.


On 12 March 2011 17:41, Nicolas Cannasse <[hidden email]> wrote:
Le 12/03/2011 13:34, basvanmeurs a écrit :

I agree that the haxelib interface could be more user-friendly. Your
modifications are indeed an improvement, but just a minor. Personally I
think that we should search the solution in a little GUI that uses the CLI.
This doesn't necessarily have to be written in HaXe. It could provide a good
overview of the installed packages, whether or not it is up to date, etc.

+1 for an haxelib UI. It can actually connect directly to the haxelib server without calling the haxelib commandline since it's based on haxe remoting.

Nicolas


--
haXe - an open source web programming language
http://haxe.org


--

haXe - an open source web programming language
http://haxe.org


--

haXe - an open source web programming language
http://haxe.org



--
Tony Polinelli
http://touchmypixel.com

--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Cauê W.
I think CLI was meant to mean Command Line Interface ; )

2011/3/12 Tarwin Stroh-Spijer <[hidden email]>
I'm giving a +1, but really think it would be best to write it in haxe, even if it may be a little more work to get a UI. Why not do it as an AIR app, that'd make easy UI and easy cross platform.

It's good for the community for people who are picking up the language to be able to edit the tools in that same language. (sometimes I lament that we don't have a haxe haxe compiler, but I totally understand why).


Tarwin Stroh-Spijer
_______________________

Touch My Pixel
http://www.touchmypixel.com/
phone: +61 3 8060 5321
_______________________


On Sun, Mar 13, 2011 at 8:53 AM, Tony Polinelli <[hidden email]> wrote:
Caue is working on the C# target - apparantly quite close. So i guess this would makw a CLI interface with remoting in the backend, a breeze!

On Sun, Mar 13, 2011 at 4:55 AM, Franco Ponticelli <[hidden email]> wrote:
They can both coexist without having to worry too much and visual tools have a bigger impacts on new users.

Franco

On Sat, Mar 12, 2011 at 5:11 PM, Pimm Hogeling <[hidden email]> wrote:
On the other hand, a client with CLI is more flexible. It can be used by an IDE, for instance. Plus a CLI can be just as user-friendly as a GUI.


On 12 March 2011 17:41, Nicolas Cannasse <[hidden email]> wrote:
Le 12/03/2011 13:34, basvanmeurs a écrit :

I agree that the haxelib interface could be more user-friendly. Your
modifications are indeed an improvement, but just a minor. Personally I
think that we should search the solution in a little GUI that uses the CLI.
This doesn't necessarily have to be written in HaXe. It could provide a good
overview of the installed packages, whether or not it is up to date, etc.

+1 for an haxelib UI. It can actually connect directly to the haxelib server without calling the haxelib commandline since it's based on haxe remoting.

Nicolas


--
haXe - an open source web programming language
http://haxe.org


--

haXe - an open source web programming language
http://haxe.org


--

haXe - an open source web programming language
http://haxe.org



--
Tony Polinelli
http://touchmypixel.com

--

haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Gamehaxe
In reply to this post by Tony Polinelli
Another option may be to write it as a web-server.  Starting the GUI
would involve starting the web-server and a browser pointing at the local  
server.
The server could relay http gets to haxe.org, and http puts could
change the local database.
I can think of one language that would make this easy.

Hugh


> Caue is working on the C# target - apparantly quite close. So i guess  
> this
> would makw a CLI interface with remoting in the backend, a breeze!
>
> On Sun, Mar 13, 2011 at 4:55 AM, Franco Ponticelli <
> [hidden email]> wrote:
>
>> They can both coexist without having to worry too much and visual tools
>> have a bigger impacts on new users.
>>
>> Franco
>>
>> On Sat, Mar 12, 2011 at 5:11 PM, Pimm Hogeling  
>> <[hidden email]>wrote:
>>
>>> On the other hand, a client with CLI is more flexible. It can be used  
>>> by
>>> an IDE, for instance. Plus a CLI can be just as user-friendly as a GUI.
>>>
>>>
>>> On 12 March 2011 17:41, Nicolas Cannasse  
>>> <[hidden email]>wrote:
>>>
>>>> Le 12/03/2011 13:34, basvanmeurs a écrit :
>>>>
>>>>  I agree that the haxelib interface could be more user-friendly. Your
>>>>> modifications are indeed an improvement, but just a minor.  
>>>>> Personally I
>>>>> think that we should search the solution in a little GUI that uses  
>>>>> the
>>>>> CLI.
>>>>> This doesn't necessarily have to be written in HaXe. It could  
>>>>> provide a
>>>>> good
>>>>> overview of the installed packages, whether or not it is up to date,
>>>>> etc.
>>>>>
>>>>
>>>> +1 for an haxelib UI. It can actually connect directly to the haxelib
>>>> server without calling the haxelib commandline since it's based on  
>>>> haxe
>>>> remoting.
>>>>
>>>> Nicolas
>>>>
>>>>
>>>> --
>>>> haXe - an open source web programming language
>>>> http://haxe.org
>>>>
>>>
>>>
>>> --
>>>
>>> haXe - an open source web programming language
>>> http://haxe.org
>>>
>>
>>
>> --
>> haXe - an open source web programming language
>> http://haxe.org
>>
>
>

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Tony Polinelli
In reply to this post by Cauê W.
>I think CLI was meant to mean Command Line Interface ; )

haha my bad ;P


On Sun, Mar 13, 2011 at 12:23 PM, Cauê Waneck <[hidden email]> wrote:
I think CLI was meant to mean Command Line Interface ; )

2011/3/12 Tarwin Stroh-Spijer <[hidden email]>
I'm giving a +1, but really think it would be best to write it in haxe, even if it may be a little more work to get a UI. Why not do it as an AIR app, that'd make easy UI and easy cross platform.

It's good for the community for people who are picking up the language to be able to edit the tools in that same language. (sometimes I lament that we don't have a haxe haxe compiler, but I totally understand why).


Tarwin Stroh-Spijer
_______________________

Touch My Pixel
http://www.touchmypixel.com/
phone: <a href="tel:%2B61%203%208060%205321" target="_blank">+61 3 8060 5321
_______________________


On Sun, Mar 13, 2011 at 8:53 AM, Tony Polinelli <[hidden email]> wrote:
Caue is working on the C# target - apparantly quite close. So i guess this would makw a CLI interface with remoting in the backend, a breeze!

On Sun, Mar 13, 2011 at 4:55 AM, Franco Ponticelli <[hidden email]> wrote:
They can both coexist without having to worry too much and visual tools have a bigger impacts on new users.

Franco

On Sat, Mar 12, 2011 at 5:11 PM, Pimm Hogeling <[hidden email]> wrote:
On the other hand, a client with CLI is more flexible. It can be used by an IDE, for instance. Plus a CLI can be just as user-friendly as a GUI.


On 12 March 2011 17:41, Nicolas Cannasse <[hidden email]> wrote:
Le 12/03/2011 13:34, basvanmeurs a écrit :

I agree that the haxelib interface could be more user-friendly. Your
modifications are indeed an improvement, but just a minor. Personally I
think that we should search the solution in a little GUI that uses the CLI.
This doesn't necessarily have to be written in HaXe. It could provide a good
overview of the installed packages, whether or not it is up to date, etc.

+1 for an haxelib UI. It can actually connect directly to the haxelib server without calling the haxelib commandline since it's based on haxe remoting.

Nicolas


--
haXe - an open source web programming language
http://haxe.org


--

haXe - an open source web programming language
http://haxe.org


--

haXe - an open source web programming language
http://haxe.org



--
Tony Polinelli
http://touchmypixel.com

--

haXe - an open source web programming language
http://haxe.org


--

haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org



--
Tony Polinelli
http://touchmypixel.com

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Nicolas Cannasse
In reply to this post by Gamehaxe
Le 13/03/2011 04:35, Hugh Sanderson a écrit :
> Another option may be to write it as a web-server. Starting the GUI
> would involve starting the web-server and a browser pointing at the
> local server.
> The server could relay http gets to haxe.org, and http puts could
> change the local database.
> I can think of one language that would make this easy.

Good idea. UI frameworks wrappers are no longer useful is you simply
have a generic browser + JS engine that can be embedded.

Best,
Nicolas

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Pimm Hogeling
In reply to this post by Justin Donaldson-3
Hey Justin,

What kind of love were you looking for? (I have plenty of love to give!)

On 13 March 2011 02:13, Justin Donaldson <[hidden email]> wrote:
It would be nice if the CLI got a little more love.  I'm doing more and more work on remote terminals these days.

-Justin

On Sat, Mar 12, 2011 at 9:11 AM, Pimm Hogeling <[hidden email]> wrote:
On the other hand, a client with CLI is more flexible. It can be used by an IDE, for instance. Plus a CLI can be just as user-friendly as a GUI.


On 12 March 2011 17:41, Nicolas Cannasse <[hidden email]> wrote:
Le 12/03/2011 13:34, basvanmeurs a écrit :

I agree that the haxelib interface could be more user-friendly. Your
modifications are indeed an improvement, but just a minor. Personally I
think that we should search the solution in a little GUI that uses the CLI.
This doesn't necessarily have to be written in HaXe. It could provide a good
overview of the installed packages, whether or not it is up to date, etc.

+1 for an haxelib UI. It can actually connect directly to the haxelib server without calling the haxelib commandline since it's based on haxe remoting.

Nicolas


--
haXe - an open source web programming language
http://haxe.org


--

haXe - an open source web programming language
http://haxe.org



--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Baluta Cristian
If i knew how or time and motivation to learn i'd do a textmate bundle like GetBundles.
Another solution would be a kind of mac app store where you can see what libs are available, what have you installed and how many needs update. This could also install the haxe itself and i'd be interested in doing this for Mac.

On Sun, Mar 13, 2011 at 2:17 PM, Pimm Hogeling <[hidden email]> wrote:
Hey Justin,

What kind of love were you looking for? (I have plenty of love to give!)


On 13 March 2011 02:13, Justin Donaldson <[hidden email]> wrote:
It would be nice if the CLI got a little more love.  I'm doing more and more work on remote terminals these days.

-Justin

On Sat, Mar 12, 2011 at 9:11 AM, Pimm Hogeling <[hidden email]> wrote:
On the other hand, a client with CLI is more flexible. It can be used by an IDE, for instance. Plus a CLI can be just as user-friendly as a GUI.


On 12 March 2011 17:41, Nicolas Cannasse <[hidden email]> wrote:
Le 12/03/2011 13:34, basvanmeurs a écrit :

I agree that the haxelib interface could be more user-friendly. Your
modifications are indeed an improvement, but just a minor. Personally I
think that we should search the solution in a little GUI that uses the CLI.
This doesn't necessarily have to be written in HaXe. It could provide a good
overview of the installed packages, whether or not it is up to date, etc.

+1 for an haxelib UI. It can actually connect directly to the haxelib server without calling the haxelib commandline since it's based on haxe remoting.

Nicolas


--
haXe - an open source web programming language
http://haxe.org


--

haXe - an open source web programming language
http://haxe.org



--
haXe - an open source web programming language
http://haxe.org



--
Băluță Cristian
http://ralcr.com
http://imagin.ro

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Pimm Hogeling
On 13 March 2011 15:21, Baluta Cristian <[hidden email]> wrote:
Another solution would be a kind of mac app store where you can see what libs are available, what have you installed and how many needs update.
This is exactly what haxelib is right now.

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Baluta Cristian
But has no UI, isn't this what we are talking about? And you can see them only if you check anyway.

On Sun, Mar 13, 2011 at 4:29 PM, Pimm Hogeling <[hidden email]> wrote:
On 13 March 2011 15:21, Baluta Cristian <[hidden email]> wrote:
Another solution would be a kind of mac app store where you can see what libs are available, what have you installed and how many needs update.
This is exactly what haxelib is right now.

--
haXe - an open source web programming language
http://haxe.org



--
Băluță Cristian
http://ralcr.com
http://imagin.ro

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Pimm Hogeling
Understood.

I'd personally love to see an application that installs haXe libraries, as well as the haXe compiler and the Neko VM. Kind-of a haxelib-hxinst fusion.

I'm also very willing to (help) develop it.

On 13 March 2011 15:38, Baluta Cristian <[hidden email]> wrote:
But has no UI, isn't this what we are talking about? And you can see them only if you check anyway.

On Sun, Mar 13, 2011 at 4:29 PM, Pimm Hogeling <[hidden email]> wrote:
On 13 March 2011 15:21, Baluta Cristian <[hidden email]> wrote:
Another solution would be a kind of mac app store where you can see what libs are available, what have you installed and how many needs update.
This is exactly what haxelib is right now.

--
haXe - an open source web programming language
http://haxe.org



--
Băluță Cristian
http://ralcr.com
http://imagin.ro

--
haXe - an open source web programming language
http://haxe.org


--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

MarcWeber
In reply to this post by Pimm Hogeling
Excerpts from Pimm Hogeling's message of Sat Mar 12 17:11:31 +0000 2011:
> On the other hand, a client with CLI is more flexible. It can be used by an
> IDE, for instance. Plus a CLI can be just as user-friendly as a GUI.

So what?

Write an API library and let people write the frontends (gui and cli).
Issue solved.

if you're going to change this allow registering upstream sources
(svn,git,mercurial,..) so that the community knows about *all* projects
available even if authors are too lazy to make proper releases.

Its not important to make the client checkout git,svn (people will
implement this soon). It important to strengthen the position of
lib.haxe.org being the only source to lookup libraries (It will never be
so.. but you get the point).

My 2 cents..
Marc Weber

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

Pimm Hogeling
On 13 March 2011 17:26, Marc Weber <[hidden email]> wrote:
So what?
Bas suggested a client with GUI, so I gave the advantages I see of a client with CLI as a counterbalance.

I for one think it's a good idea have git clone and svn export functionality built into the library application. This is kind-of like the nightly builds we have of the haXe compiler.

--
haXe - an open source web programming language
http://haxe.org
Reply | Threaded
Open this post in threaded view
|

Re: Humanised haxelib (patch)

MarcWeber
> nightly builds we have of the haXe compiler.
> I for one think it's a good idea have *git clone* and *svn
> export*functionality built into the library application. This is
This will naturally follow. Its important to make it easy for all
library writers to register their git ,hg ,.. urls on lib.haxe.org.

Marc Weber

--
haXe - an open source web programming language
http://haxe.org