1 |
> > - image to vector applications like autotrace resp. potrace |
2 |
|
3 |
> Ok. Now I get what you want. For the image converting applications, |
4 |
> you might want to go for some 'drop file on' solution, like |
5 |
> Photoshop has. You simply drop a file on the icon, and it's being |
6 |
> converted somehow. I think this is quite generic somehow. Interesting! |
7 |
|
8 |
Nice idea, but currently not doable, I am afraid. My ObjectiveC / Cocoa |
9 |
knowledge is not upto task to do something as complicated as drag-and-drop |
10 |
programming ;) |
11 |
|
12 |
> > More complex GUIs I could imagine e.g for |
13 |
> > - ImageMagick |
14 |
|
15 |
> For sure! But aren't there attempts for this yet? I mean, is this idea |
16 |
> brand new, or are there already a few apps that are some sort of skin |
17 |
> for ImageMagick, but just written in something that doesn't work very |
18 |
> well on OSX? |
19 |
|
20 |
Most (GUI) attempts I know try to wrap around the Image Magick API and try |
21 |
to build a document centric (or a type manager / image database) |
22 |
For document centric there exists GraphicConverter, while for type manager |
23 |
there exist iPhoto. |
24 |
Both are not really interesting to me. |
25 |
|
26 |
What I miss on Mac is something like IrfanView's (on Windows) batch |
27 |
conversion GUI. |
28 |
|
29 |
> This sounds exactly like the properties of Automator. I never toyed |
30 |
> with it, but it it sold as ultimate tool for 'intelligent' task |
31 |
> automation. Maybe generating Automator scripts would be a first step? |
32 |
|
33 |
I think Automator is a dead end, at least currently. |
34 |
- Tiger only |
35 |
- only linear workflows |
36 |
- I have not so many recurring tasks which would require building automator |
37 |
like workflows. |
38 |
|
39 |
> > - a simple list where you can see the list of latest ebuild changes, |
40 |
> > something like "keep your system uptodate" |
41 |
|
42 |
> Like the FinkCommander screen, right? |
43 |
|
44 |
In fact more something like that ;) http://www.gnomejournal.org/images/45.png |
45 |
|
46 |
> > Something like a rich client application for packages.gentoo.org, with |
47 |
> > the added functionality to start a emerge, emerge -C, emerge -u for the |
48 |
> > selected packages |
49 |
|
50 |
> Ok, so that's the full FinkCommander functionality. |
51 |
Yes. |
52 |
|
53 |
> > The last two GUIs you can see in some apt frontends, like e.g in Ubuntu |
54 |
> > (written in C / Gtk) |
55 |
> > |
56 |
> > I have never seen FinkCommander |
57 |
|
58 |
> Good, good, good!!!! :) However, you should take a look at their |
59 |
> screenshots, because it's exactly what you describe. |
60 |
|
61 |
FinkCommander seems to be a good candidate for a "data waste / information |
62 |
overload" type application. I don't think such a GUI is really suitable |
63 |
for a large repository like Gentoo, with thousands of applications. |
64 |
Besides, I am more a fan of icon list views or OpenStep like multi-column |
65 |
lists, instead of table based lists... |
66 |
|
67 |
> OT: did you install Python 2.4 in the end? |
68 |
|
69 |
No. If I currently need source packages which are not available for |
70 |
Gentoo, I either install manually into /usr/local, or into really parallel |
71 |
branches like /gnu. |
72 |
progressive mode, or a Fink style managed /sw hierarchy, ar currently no |
73 |
option for me. |
74 |
|
75 |
> > 1) a port of Renaissance to cocoa. Because there already exist a binary |
76 |
> > distribution, porting must be possible. Perhaps a special USE flag is |
77 |
> > needed, for somebody who want to keep parallel versions for GNUstep/X |
78 |
> > and Cocoa in parallel. |
79 |
|
80 |
> The keyword aqua comes to mind... Kito and I had a discussion about it |
81 |
> the other day, but the idea is right I think. |
82 |
|
83 |
Fine. What is needed to get this started? I could try to compile / emerge |
84 |
Renaissance and try to extract suitable flags for a Cocoa based ebuild. |
85 |
|
86 |
> > good if they are not Macos specific, but could be used in Gentoo / Linux. |
87 |
> > Possbly of interest for GNUstep. |
88 |
|
89 |
> Sure. Objective-C is just something which you should have compiled when |
90 |
> emerging gcc, but GNUstep users (like me, surprise, eh?) will probably |
91 |
> be able to benefit from these efforts. |
92 |
|
93 |
I would much prefer to be able to use a package.provided ObjectiveC |
94 |
compiler... |
95 |
|
96 |
> Question remains who else could benefit from it, because the number of |
97 |
> Gentoo/GNUstep users is rather small, IMHO. |
98 |
|
99 |
Good question, but something I cannot answer. My Python knowledge is |
100 |
nearly zero. |
101 |
|
102 |
> If I recall correctly, there are special eclasses that for instance |
103 |
> allow to place an icon on the desktop of the user (transparently to what |
104 |
> window manager the user uses). |
105 |
|
106 |
If you use py2app, you get a app folder in the dist sub folder of your |
107 |
python app root. I thought it was a good idea to copy this app folder |
108 |
application into something like /Applications/Gentoo, in the installation |
109 |
step of emerge. |
110 |
No need to toy around with links, at least not on OSX, I think. |
111 |
|
112 |
> The GentooUI (pronounced as 'gentoo-e' ? :p ), or iGentoo can be |
113 |
> developed in a separate track from the others. However, it would be a |
114 |
> waste if it would be developed such that nothing of it can be reused for |
115 |
> other Gentoo/X projects. |
116 |
|
117 |
Agreed on the "separate track". |
118 |
I am not quite sure about the other part. From what I see, a GentooUI tool |
119 |
(or at list something like a FinkCommander clone) is not much more than a |
120 |
emerge output parser and pretty printer ;) |
121 |
This means that the interesting / backend parts are already re-useable |
122 |
(even more so if there exist an API instead of having to grep console |
123 |
output), while the frontend part mostly are toolkit specific and not |
124 |
useable. |
125 |
|
126 |
Regards |
127 |
Dirk |
128 |
-- |
129 |
gentoo-osx@g.o mailing list |