Hi,
Additionally I found these bugs:
- TexMacs crashes on some special Symbols like "¡ ß" etc.
- The Drawing tools has redraw Errors.
- Open a Document ask if I would like to overwrite it...
The time I can spend on texmacs is also very limited... And
additionally I did never write a Cocoa app... just some others.
But I will see what I can do.
I think it would be a good thing to tell the world of this coca port.
I think this will automatically "generate" some helping hands... the
hard part of the work is done, in my oppinion. the other things are
little steps.
Do you also like patches instead of cvs?
For first I would add the NSInteger things...
(But ask me not WHEN the this patch will arrive...)
greetings
andi
Am 11.06.2008 um 16:57 schrieb [EMAIL PROTECTED]:
Hi,
On Jun 9, 2008, at 5:02 PM, Andreas Körner wrote:
Ok,
I got It compiled for Myself:
I used the following tricks:
first at all:
fink -b install texmacs - But I thinks thats not needed
in src/Plugin/Cocoa:
#define NSInteger int
#define NSUInteger uint
I think thats some kind of stupid but as NSInteger and NSUInteger
where not defined in Apples Docs I found this as a good workaround
because NSInteger was not defined but used.
I think NSInteger has been introduced in 10.5. I developer the
cocoa port under Leopard (at least in the last times) and I hadn't
the opportunity to test it on 10.4.
Next I found that imlib2.hpp needed X11/... this is in the Apple
SDK, but not in the Include path
As I didn't know how to change the Include path I
ln -s /Developer/SDKs/MacOSX10.3.9.sdk/usr/X11R6/include/X11 /sw/
include/X11
than a simple
./configure --enable-cocoa
make
make BUNDLE # or make DISKIMAGE
works (but it's VERY unstable at the moment)
Ok ... how can I help to improve the mac port?
the port is in a very early stage. My first goal has been to
implement roughly the basic stuff, also to get acquainted with the
source code. Joris has made a very nice work in separating the
different layers of the GUI and it has been not so difficult to
make TeXmacs run natively under cocoa.
However there are many weak points:
1) the rendering mechanism which keeps the UI up to date while
typing is not as smooth as in the X11 version. In particular at the
moment the shadow rendering mechanism is virtually disabled (in the
sense that the shadow drawable is actually the real drawable)
2) the support for the keyboard is primitive. Mac keyboard allows
very complex patterns (like the key sequence required to produce
chars like î on english keyboards). We must take inspiration from
other ports to have a sensible way of doing it. (e.g. look at the
cocoa port of Emacs).
3) all widgets for opening, saving, printing must be correctly
implemented. At the moment they are just mock up implemented with
standard parts which does not fit very well the logic of texmacs.
4) menus are working but improvements should be possible (caching?,
better structure for the code,...)
5) better handling of fonts, possibility to use directly system
fonts (or open-type versions) instead of the bitmap fonts created
by freetype or pk fonts
6) there are problems with images
These are the priorities as far as I'm concerned. For personal
reasons I'm not able at the moment to spend much time on the port,
but I hope to do so within some months. But I would be glad if
somebody would like to join the effort. At the moment the cocoa
code base is not very large and it is a good moment to join the
project since it will not take much effort to have a complete
understanding of the port (and is also an easy way to start
understanding the TeXmacs codebase).
Best,
Massimiliano Gubinelli
greetings
andi
_______________________________________________
Texmacs-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/texmacs-dev
_______________________________________________
Texmacs-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/texmacs-dev
_______________________________________________
Texmacs-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/texmacs-dev
